Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First pass PipelineGraph UI component #732

Merged
merged 1 commit into from
Nov 13, 2019

Conversation

AlanGreene
Copy link
Member

Changes

#675

Add PipelineGraph UI component using elkjs and vx.
It does not currently support user interaction (zoom, pan, click, etc.)
but this will come in future PRs.

It also does not currently render steps when the tasks are expanded (see screenshot).

Add storybook stories to cover the two main components:

  • Node: represents a node in the graph (Task or Step)
  • PipelineGraph: collection of Nodes + Links

image

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide
for more details.

Add PipelineGraph UI component using elkjs and vx.
It does not currently support user interaction (zoom, pan, click, etc.)
but this will come in future PRs.

Add storybook stories to cover the two main components:
- Node: represents a node in the graph (Task or Step)
- PipelineGraph: collection of Nodes + Links
@tekton-robot tekton-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Nov 13, 2019
Copy link
Member

@steveodonovan steveodonovan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small thing, otherwise looks good

let StatusIcon;
if (type === 'Task' || status === 'error') {
switch (status) {
case 'error':
Copy link
Member

@steveodonovan steveodonovan Nov 13, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reads a little strange, make sense to move status === error to its own conditional above ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had that originally but didn't like the duplication and potential for inconsistency in the icons used, we can have a Task with status 'error' or a Step with status 'error'. Tasks always show an icon, Steps only show icon on error.

Open to any suggestions to clean this up.

Copy link
Member

@steveodonovan steveodonovan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 13, 2019
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: steveodonovan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 13, 2019
@tekton-robot tekton-robot merged commit bbab8b1 into tektoncd:master Nov 13, 2019
@AlanGreene AlanGreene deleted the graph_nodes branch November 13, 2019 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants